-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: improve svm landing time metric #373
Conversation
guibescos
commented
Jan 31, 2025
•
edited
Loading
edited
- make buckets that match what we see in production better
- start measuring before the first send_transaction
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
auction-server/src/server.rs
Outdated
@@ -135,8 +135,20 @@ async fn fetch_access_tokens(db: &PgPool) -> HashMap<models::AccessTokenToken, m | |||
.collect() | |||
} | |||
|
|||
pub const TRANSACTION_LANDING_TIME_SVM_METRIC: &str = "transaction_landing_time_seconds_svm"; | |||
const TRANSACTION_LANDING_TIME_SVM_BUCKETS: &[f64; 14] = &[ | |||
0.1, 0.25, 0.5, 0.75, 1.0, 1.25, 1.5, 1.75, 2.0, 2.25, 2.5, 3.75, 5.0, 10.0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is my bucket list suggestion:
[0.5, 1.0, 2.0, 4.0, 6.0, 8.0, 10.0, 15.0, 20.0, 30.0, 40.0, 50.0, 60.0]
We need to know more about instances more than 10 seconds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@m30m wanted more granularity between 1 and 2.5 because we see currently of transactions there, but I also added the 20 and 40 bucket